Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cba4abdc100897290392f0dd1b3163a2752c64e443b580ad34e939afc84bdb9

Tx prefix hash: 6e57a10f32085a3da781eb4f9a57f8808efadc8115ddc72b7492962001761449
Tx public key: 901f805c8d4e0ca89dcc302b816a5cb0bf41eb4e25929c981c120abcf73b63d4
Timestamp: 1730581704 Timestamp [UCT]: 2024-11-02 21:08:24 Age [y:d:h:m:s]: 01:013:22:19:59
Block: 1145197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268386 RingCT/type: yes/0
Extra: 01901f805c8d4e0ca89dcc302b816a5cb0bf41eb4e25929c981c120abcf73b63d4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56dbab97d7674ff0a7e74ce0be8b884782890cc1fcab1beee2939eef4fb56ce6 0.600000000000 1629594 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": 1145207, "vin": [ { "gen": { "height": 1145197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56dbab97d7674ff0a7e74ce0be8b884782890cc1fcab1beee2939eef4fb56ce6" } } ], "extra": [ 1, 144, 31, 128, 92, 141, 78, 12, 168, 157, 204, 48, 43, 129, 106, 92, 176, 191, 65, 235, 78, 37, 146, 156, 152, 28, 18, 10, 188, 247, 59, 99, 212, 2, 17, 0, 0, 0, 3, 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