Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dc1603efb777b943b1c72fcb8f85c0e4882e4472671bdcab19d4dbb351a262f2

Tx prefix hash: bb2e79fe6f0d9f103cd50e8450a27f43cf05a5140bcfb09cf5bd7be5006a1a70
Tx public key: 3219558df6583d511235477fda6759184f55e5b6c98bd8bf28fb47964a3832fb
Timestamp: 1697979451 Timestamp [UCT]: 2023-10-22 12:57:31 Age [y:d:h:m:s]: 01:159:02:15:33
Block: 875204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374708 RingCT/type: yes/0
Extra: 013219558df6583d511235477fda6759184f55e5b6c98bd8bf28fb47964a3832fb02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.772833347000 dcy

stealth address amount amount idx
00: 99261c2da21db26dea0a34879109ba4ec91d38c65700e30cd859e30c0d7b1875 0.772833347000 1330448 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 875214, "vin": [ { "gen": { "height": 875204 } } ], "vout": [ { "amount": 772833347, "target": { "key": "99261c2da21db26dea0a34879109ba4ec91d38c65700e30cd859e30c0d7b1875" } } ], "extra": [ 1, 50, 25, 85, 141, 246, 88, 61, 81, 18, 53, 71, 127, 218, 103, 89, 24, 79, 85, 229, 182, 201, 139, 216, 191, 40, 251, 71, 150, 74, 56, 50, 251, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8