Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28f5bac121499362c81a8227ab39b928597b3613943bcbd2cf099a4f4c76c14a

Tx prefix hash: 884e3145815a1101708a83dfb143180c21d893d3b476de2bbfc844d9885bd6a2
Tx public key: 748b956ae0d681135ef3be3efbfb817e76545486f7ae5f58e2edbd2f17b7081e
Timestamp: 1741156444 Timestamp [UCT]: 2025-03-05 06:34:04 Age [y:d:h:m:s]: 00:063:21:43:56
Block: 1232492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45704 RingCT/type: yes/0
Extra: 01748b956ae0d681135ef3be3efbfb817e76545486f7ae5f58e2edbd2f17b7081e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c513d97edde2d249bd7699c98d5ca60bf381722d23d3f3d1613b32873b3f642a 0.600000000000 1719405 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": 1232502, "vin": [ { "gen": { "height": 1232492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c513d97edde2d249bd7699c98d5ca60bf381722d23d3f3d1613b32873b3f642a" } } ], "extra": [ 1, 116, 139, 149, 106, 224, 214, 129, 19, 94, 243, 190, 62, 251, 251, 129, 126, 118, 84, 84, 134, 247, 174, 95, 88, 226, 237, 189, 47, 23, 183, 8, 30, 2, 17, 0, 0, 0, 1, 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