Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f62dd23095865dbbe187b141b1c16b98cb2dfbef8aa814c9ceb18114089a0e

Tx prefix hash: 7acb8241661fad8a842c4d63f3ef7c3ae1c2d978cd5925c0752a709c4a6538c5
Tx public key: bf2c0224d43827fd98955e438fd0202ad534f6a807a7779e8eebb017296fc26e
Timestamp: 1709152492 Timestamp [UCT]: 2024-02-28 20:34:52 Age [y:d:h:m:s]: 01:015:04:25:04
Block: 967633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271867 RingCT/type: yes/0
Extra: 01bf2c0224d43827fd98955e438fd0202ad534f6a807a7779e8eebb017296fc26e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d7b20d7451f0670df4c574b6c5d260dc19cf22ab782551dfc2043b45550a19c 0.600000000000 1427416 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": 967643, "vin": [ { "gen": { "height": 967633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d7b20d7451f0670df4c574b6c5d260dc19cf22ab782551dfc2043b45550a19c" } } ], "extra": [ 1, 191, 44, 2, 36, 212, 56, 39, 253, 152, 149, 94, 67, 143, 208, 32, 42, 213, 52, 246, 168, 7, 167, 119, 158, 142, 235, 176, 23, 41, 111, 194, 110, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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