Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d34f5a520a4cb1e68655765519a776dbf88831818b90c3a16ae2df6036b8488

Tx prefix hash: ea6dfdeeae9dfc72151158a2001e308e6035acb1a07bb0ddac9fcafb5685ff92
Tx public key: 25dbe89e588edb4ada9b7d906a1b67e5bfc5d813666c6b3edfce8617a8873e00
Timestamp: 1702791433 Timestamp [UCT]: 2023-12-17 05:37:13 Age [y:d:h:m:s]: 01:034:08:38:41
Block: 914887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285873 RingCT/type: yes/0
Extra: 0125dbe89e588edb4ada9b7d906a1b67e5bfc5d813666c6b3edfce8617a8873e0002110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f33fe173cb96f18bb27d9054a8e4cccd62dde5fe87c174d9c9a66870658eade 0.600000000000 1372239 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": 914897, "vin": [ { "gen": { "height": 914887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f33fe173cb96f18bb27d9054a8e4cccd62dde5fe87c174d9c9a66870658eade" } } ], "extra": [ 1, 37, 219, 232, 158, 88, 142, 219, 74, 218, 155, 125, 144, 106, 27, 103, 229, 191, 197, 216, 19, 102, 108, 107, 62, 223, 206, 134, 23, 168, 135, 62, 0, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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