Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be57e9c20e247bf12670b882c0cb47dfd2dbaba896bbb9dce142c09c5201e63f

Tx prefix hash: 6ebc75c19ac5671d91d9138f5ce97ea19969a28f6bc78a6c628f6b44696827c3
Tx public key: 167d1f8db0ba7bdaedd3f8fb9d18b68b9921a16571539788024af5acaba03e6b
Timestamp: 1674637433 Timestamp [UCT]: 2023-01-25 09:03:53 Age [y:d:h:m:s]: 01:353:03:49:33
Block: 682359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513389 RingCT/type: yes/0
Extra: 01167d1f8db0ba7bdaedd3f8fb9d18b68b9921a16571539788024af5acaba03e6b0211000000045029cbac000000000000000000

1 output(s) for total of 3.365590797000 dcy

stealth address amount amount idx
00: 3f03abd07da686e0a531b7fa804909e213b0a0dc821bb094c4964f29719be2d8 3.365590797000 1124478 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": 682369, "vin": [ { "gen": { "height": 682359 } } ], "vout": [ { "amount": 3365590797, "target": { "key": "3f03abd07da686e0a531b7fa804909e213b0a0dc821bb094c4964f29719be2d8" } } ], "extra": [ 1, 22, 125, 31, 141, 176, 186, 123, 218, 237, 211, 248, 251, 157, 24, 182, 139, 153, 33, 161, 101, 113, 83, 151, 136, 2, 74, 245, 172, 171, 160, 62, 107, 2, 17, 0, 0, 0, 4, 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