Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d51faf2d66204a7cd6863ed03e796d8d310d7997e458983c44a24eb7416e41bf

Tx prefix hash: 353af45ba5324bf45f7dc3a6c21bf477941a3234f20ed19611cd0f4152c9a041
Tx public key: d678b81363f9a6c55c3daea08cb259122e3c9d9f716bf30c4a3be7600255d5c2
Timestamp: 1577710048 Timestamp [UCT]: 2019-12-30 12:47:28 Age [y:d:h:m:s]: 05:065:15:18:25
Block: 35027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196670 RingCT/type: yes/0
Extra: 01d678b81363f9a6c55c3daea08cb259122e3c9d9f716bf30c4a3be7600255d5c20211000000028a2ee0d9000000000000000000

1 output(s) for total of 469.831210820000 dcy

stealth address amount amount idx
00: d60ff2080f74d8785934ac0878a41bd3ec83ad0fe2e94b10a6345465d67b18e2 469.831210820000 59012 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": 35037, "vin": [ { "gen": { "height": 35027 } } ], "vout": [ { "amount": 469831210820, "target": { "key": "d60ff2080f74d8785934ac0878a41bd3ec83ad0fe2e94b10a6345465d67b18e2" } } ], "extra": [ 1, 214, 120, 184, 19, 99, 249, 166, 197, 92, 61, 174, 160, 140, 178, 89, 18, 46, 60, 157, 159, 113, 107, 243, 12, 74, 59, 231, 96, 2, 85, 213, 194, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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