Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7154e4cf71536ed64a59ffef4788f332bc3b493ca5dc8fd62e9efb16fda920f2

Tx prefix hash: b75bb5e76f329932b9b0b0288e13f8978c30b02e5a2acdf77a9e95c6d810f103
Tx public key: 1babea40426086df720a9a3db5b8df0b41106a46c48820964141c26875fb1bbc
Timestamp: 1702916288 Timestamp [UCT]: 2023-12-18 16:18:08 Age [y:d:h:m:s]: 01:330:02:47:57
Block: 915925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494784 RingCT/type: yes/0
Extra: 011babea40426086df720a9a3db5b8df0b41106a46c48820964141c26875fb1bbc021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5de95891c4b547a830d962f875cbfa8fc7551d0b51ea96627d80f624da46cd5e 0.600000000000 1373359 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": 915935, "vin": [ { "gen": { "height": 915925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5de95891c4b547a830d962f875cbfa8fc7551d0b51ea96627d80f624da46cd5e" } } ], "extra": [ 1, 27, 171, 234, 64, 66, 96, 134, 223, 114, 10, 154, 61, 181, 184, 223, 11, 65, 16, 106, 70, 196, 136, 32, 150, 65, 65, 194, 104, 117, 251, 27, 188, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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