Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87c5d5e07de2bb7c45ee7ac66e36dfac7d4a50084b16bb81b4c416e83665363a

Tx prefix hash: cf9f9f901b47fa2e776a384631bde10565b006934ff38afa2cd52242a43462b1
Tx public key: caf4d431e2da5b770856b669e798c7c825900d0ced75b9ea29212559bd54c52d
Timestamp: 1718746724 Timestamp [UCT]: 2024-06-18 21:38:44 Age [y:d:h:m:s]: 00:273:13:52:58
Block: 1047167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195505 RingCT/type: yes/0
Extra: 01caf4d431e2da5b770856b669e798c7c825900d0ced75b9ea29212559bd54c52d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5ad12b0b34cb423e0c1e0fad44ed8fb96848a78c21f315b043028b90fa9f4ae 0.600000000000 1516986 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": 1047177, "vin": [ { "gen": { "height": 1047167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5ad12b0b34cb423e0c1e0fad44ed8fb96848a78c21f315b043028b90fa9f4ae" } } ], "extra": [ 1, 202, 244, 212, 49, 226, 218, 91, 119, 8, 86, 182, 105, 231, 152, 199, 200, 37, 144, 13, 12, 237, 117, 185, 234, 41, 33, 37, 89, 189, 84, 197, 45, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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