Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f48beb6be39cdfe01c55c7585b6aa6ce5803bdd3ede6528ab3a3ffc8febea350

Tx prefix hash: bcbd8b58929b4b5fdfa5f91e94eac15bcd7fac902c791107189fcf092493189c
Tx public key: 5d1edc8f19fe76a5cc867450cf6f71c8d25daa6dc8e8a18d456df23a95f21d81
Timestamp: 1680895023 Timestamp [UCT]: 2023-04-07 19:17:03 Age [y:d:h:m:s]: 02:000:02:31:20
Block: 733812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522005 RingCT/type: yes/0
Extra: 015d1edc8f19fe76a5cc867450cf6f71c8d25daa6dc8e8a18d456df23a95f21d810211000000015029cbac000000000000000000

1 output(s) for total of 2.272879706000 dcy

stealth address amount amount idx
00: 383ab1a28ca3720e6776eccb54a535dbeffcd0b5354c56390875f28cf25558b2 2.272879706000 1179919 of 0

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": 733822, "vin": [ { "gen": { "height": 733812 } } ], "vout": [ { "amount": 2272879706, "target": { "key": "383ab1a28ca3720e6776eccb54a535dbeffcd0b5354c56390875f28cf25558b2" } } ], "extra": [ 1, 93, 30, 220, 143, 25, 254, 118, 165, 204, 134, 116, 80, 207, 111, 113, 200, 210, 93, 170, 109, 200, 232, 161, 141, 69, 109, 242, 58, 149, 242, 29, 129, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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