Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 458194ac32931c3598460a83556f265c9f42abf0b395931a9d02c1eaea81f35a

Tx prefix hash: 6c7850bc37d2e07ccf2d145867ab21122933d062704686b71eb396593c716bc5
Tx public key: e4f4fee24f6994e7222c35fe9196a7f7ed62d53dbb8bca19974ff9d069ef6992
Timestamp: 1714301169 Timestamp [UCT]: 2024-04-28 10:46:09 Age [y:d:h:m:s]: 01:040:20:29:30
Block: 1010308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290163 RingCT/type: yes/0
Extra: 01e4f4fee24f6994e7222c35fe9196a7f7ed62d53dbb8bca19974ff9d069ef699202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbf65d20e5e63d7a0a00ecc1c9bb991f4c747e918eb819e6d6c202bae3fa8435 0.600000000000 1472222 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": 1010318, "vin": [ { "gen": { "height": 1010308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbf65d20e5e63d7a0a00ecc1c9bb991f4c747e918eb819e6d6c202bae3fa8435" } } ], "extra": [ 1, 228, 244, 254, 226, 79, 105, 148, 231, 34, 44, 53, 254, 145, 150, 167, 247, 237, 98, 213, 61, 187, 139, 202, 25, 151, 79, 249, 208, 105, 239, 105, 146, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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