Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f25f2612571fbb1807c31eb0c663e8b78c36a233a3d44c19fe21621a7ee29e62

Tx prefix hash: d5bdad9c2ded3f65db6a582cc510ce38a3934056bce3b0499466d60f93ce583d
Tx public key: fdcc95e25b3ad6f04678d08952067b8319fbd4cb4083e5e02253ee9efd33cba9
Timestamp: 1670291259 Timestamp [UCT]: 2022-12-06 01:47:39 Age [y:d:h:m:s]: 02:159:10:45:50
Block: 646340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 635680 RingCT/type: yes/0
Extra: 01fdcc95e25b3ad6f04678d08952067b8319fbd4cb4083e5e02253ee9efd33cba90211000000027e406890000000000000000000

1 output(s) for total of 4.430036081000 dcy

stealth address amount amount idx
00: 907066de4648f3294aeeffa5ead6312815f2c7290c3ef96b62d83007e2141fde 4.430036081000 1086557 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": 646350, "vin": [ { "gen": { "height": 646340 } } ], "vout": [ { "amount": 4430036081, "target": { "key": "907066de4648f3294aeeffa5ead6312815f2c7290c3ef96b62d83007e2141fde" } } ], "extra": [ 1, 253, 204, 149, 226, 91, 58, 214, 240, 70, 120, 208, 137, 82, 6, 123, 131, 25, 251, 212, 203, 64, 131, 229, 224, 34, 83, 238, 158, 253, 51, 203, 169, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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