Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 919dd63598515e7209090118d8ea8504969b702cb2839a0439da74e37fd762f1

Tx prefix hash: aa7e1ceb94295bd5e153b2d0b8488e08453fb53d4389dd52eafa704ceb7acad0
Tx public key: 3c9a9a54154d25665ea3b5b93cf80baf5e7047bacf65ef0546e12554de7f1849
Timestamp: 1725609305 Timestamp [UCT]: 2024-09-06 07:55:05 Age [y:d:h:m:s]: 01:063:08:32:50
Block: 1104066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303702 RingCT/type: yes/0
Extra: 013c9a9a54154d25665ea3b5b93cf80baf5e7047bacf65ef0546e12554de7f1849021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2aa945b3e0e4fbac5741cfe32ce3eb785b0bcd2b9578f0f5eb1f8fa6a8f222b 0.600000000000 1581125 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": 1104076, "vin": [ { "gen": { "height": 1104066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2aa945b3e0e4fbac5741cfe32ce3eb785b0bcd2b9578f0f5eb1f8fa6a8f222b" } } ], "extra": [ 1, 60, 154, 154, 84, 21, 77, 37, 102, 94, 163, 181, 185, 60, 248, 11, 175, 94, 112, 71, 186, 207, 101, 239, 5, 70, 225, 37, 84, 222, 127, 24, 73, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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