Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd578ac8caaadb7dc4bdd9ceb68eb810fb4609a647ec4daef9a7dd0964d8d6f

Tx prefix hash: 7dde4048f853b677c7837a1904d99b1cd89cab5b50a73709cdc00b6b0985c0b3
Tx public key: 10dc4af7e1c4ca4249175832db2c4c3fcb380429b76a7de443b0b09204b55ac2
Timestamp: 1747695722 Timestamp [UCT]: 2025-05-19 23:02:02 Age [y:d:h:m:s]: 00:248:03:10:37
Block: 1286617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175002 RingCT/type: yes/0
Extra: 0110dc4af7e1c4ca4249175832db2c4c3fcb380429b76a7de443b0b09204b55ac20211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fd59550625a99dc7810ccfd3ef53408e0eecc8373ae9807267d380f720197f2 0.600000000000 1774084 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": 1286627, "vin": [ { "gen": { "height": 1286617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fd59550625a99dc7810ccfd3ef53408e0eecc8373ae9807267d380f720197f2" } } ], "extra": [ 1, 16, 220, 74, 247, 225, 196, 202, 66, 73, 23, 88, 50, 219, 44, 76, 63, 203, 56, 4, 41, 183, 106, 125, 228, 67, 176, 176, 146, 4, 181, 90, 194, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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