Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bdbe14c4898d520f77d636ad352541361e3da42ee1a67bb63cbe4bc6bc83979

Tx prefix hash: b910d123ccd95297527e3d0ee5daef25aa3cef872cc7b04636992d13bdb1b390
Tx public key: e60ab1577e3e6ec1498f1c801754eaa14b3c0fab390665976a123241d6bfd1ba
Timestamp: 1727586359 Timestamp [UCT]: 2024-09-29 05:05:59 Age [y:d:h:m:s]: 00:181:07:12:17
Block: 1120455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129372 RingCT/type: yes/0
Extra: 01e60ab1577e3e6ec1498f1c801754eaa14b3c0fab390665976a123241d6bfd1ba02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 756406b0b1e59ca0b86be01b67ad78fac904b414b7a6d5a193d8a77b4d8ad592 0.600000000000 1602378 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": 1120465, "vin": [ { "gen": { "height": 1120455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756406b0b1e59ca0b86be01b67ad78fac904b414b7a6d5a193d8a77b4d8ad592" } } ], "extra": [ 1, 230, 10, 177, 87, 126, 62, 110, 193, 73, 143, 28, 128, 23, 84, 234, 161, 75, 60, 15, 171, 57, 6, 101, 151, 106, 18, 50, 65, 214, 191, 209, 186, 2, 17, 0, 0, 0, 5, 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