Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 449413f88f77a8ec1255ddc356142cdde625f642513645f286928f8ffc1db2d1

Tx prefix hash: d983fa2a9fb66f2f87feab04c6dfcb2f5025bbb8a6c20b433131e33e9f3ea3ee
Tx public key: 121bb11697cf1dcfcb544fcace0c428095cc7e8fa1ff3dc6e2ec7aba620caf52
Timestamp: 1720864349 Timestamp [UCT]: 2024-07-13 09:52:29 Age [y:d:h:m:s]: 00:269:03:45:21
Block: 1064740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192271 RingCT/type: yes/0
Extra: 01121bb11697cf1dcfcb544fcace0c428095cc7e8fa1ff3dc6e2ec7aba620caf5202110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 471e8b66efc5b29568dcadd4f239bff0b0850b3c32a41a2534859bed55b5f3c3 0.600000000000 1535275 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": 1064750, "vin": [ { "gen": { "height": 1064740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "471e8b66efc5b29568dcadd4f239bff0b0850b3c32a41a2534859bed55b5f3c3" } } ], "extra": [ 1, 18, 27, 177, 22, 151, 207, 29, 207, 203, 84, 79, 202, 206, 12, 66, 128, 149, 204, 126, 143, 161, 255, 61, 198, 226, 236, 122, 186, 98, 12, 175, 82, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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