Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ce79dc5dd636cc49758fe55a6235836da4db116702d14d1078dafbe78068c5

Tx prefix hash: cf70e65d8afee964981c6839984ba7aac7d15a07918094e1a4abee98c4a8c4c5
Tx public key: 00e0b50a8d7d5f7c1de1e1d79e4da75b3a14edcc97eb51b2a26744f1c1bcb3fb
Timestamp: 1734525419 Timestamp [UCT]: 2024-12-18 12:36:59 Age [y:d:h:m:s]: 00:185:14:17:57
Block: 1177891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132265 RingCT/type: yes/0
Extra: 0100e0b50a8d7d5f7c1de1e1d79e4da75b3a14edcc97eb51b2a26744f1c1bcb3fb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0cd1dc7a4b75bf93342790c4b7ae44132462328e8b6cbe75fe7d30433c00fe9 0.600000000000 1664272 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": 1177901, "vin": [ { "gen": { "height": 1177891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0cd1dc7a4b75bf93342790c4b7ae44132462328e8b6cbe75fe7d30433c00fe9" } } ], "extra": [ 1, 0, 224, 181, 10, 141, 125, 95, 124, 29, 225, 225, 215, 158, 77, 167, 91, 58, 20, 237, 204, 151, 235, 81, 178, 162, 103, 68, 241, 193, 188, 179, 251, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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