Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d98d8df2ae7cf50be38865263c7aa15665656aed1a552fe76ce82296d554e2b6

Tx prefix hash: cdc96ab5e345cf135df7e50049a8d73aff5345dccacfe89cac29c885b5c870f7
Tx public key: 3b160a7a016a8b417e211cc8943e1b9d5bd3018530931d41526ca17c3d5aef11
Timestamp: 1746096211 Timestamp [UCT]: 2025-05-01 10:43:31 Age [y:d:h:m:s]: 00:204:13:38:29
Block: 1273376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143929 RingCT/type: yes/0
Extra: 013b160a7a016a8b417e211cc8943e1b9d5bd3018530931d41526ca17c3d5aef11021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8e08e6241a6214f3cde6634e5f614cdbdee7e5714557d8c978fd1ad99ce3843 0.600000000000 1760657 of 15

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": 1273386, "vin": [ { "gen": { "height": 1273376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8e08e6241a6214f3cde6634e5f614cdbdee7e5714557d8c978fd1ad99ce3843" } } ], "extra": [ 1, 59, 22, 10, 122, 1, 106, 139, 65, 126, 33, 28, 200, 148, 62, 27, 157, 91, 211, 1, 133, 48, 147, 29, 65, 82, 108, 161, 124, 61, 90, 239, 17, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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