Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1872403d28769c27e5c0dfb1de51e8b9caedaf163ba732707ab9322587b0145f

Tx prefix hash: fe3e1a7d054bda71206b48b0bc9f58a68384228c5c8e498f9128140a81aaa382
Tx public key: b9bcb30564ac6763bcc68ab6d192f9f075d098502a8c14cb735c937b845ecbb4
Timestamp: 1578649550 Timestamp [UCT]: 2020-01-10 09:45:50 Age [y:d:h:m:s]: 05:136:00:21:40
Block: 42460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247367 RingCT/type: yes/0
Extra: 01b9bcb30564ac6763bcc68ab6d192f9f075d098502a8c14cb735c937b845ecbb402110000000a8a2ee0d9000000000000000000

1 output(s) for total of 444.044395296000 dcy

stealth address amount amount idx
00: 26ffaf3664516d7712500299f14635895208c8e53c73b6904b2cfcf51f75c1cf 444.044395296000 76509 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": 42470, "vin": [ { "gen": { "height": 42460 } } ], "vout": [ { "amount": 444044395296, "target": { "key": "26ffaf3664516d7712500299f14635895208c8e53c73b6904b2cfcf51f75c1cf" } } ], "extra": [ 1, 185, 188, 179, 5, 100, 172, 103, 99, 188, 198, 138, 182, 209, 146, 249, 240, 117, 208, 152, 80, 42, 140, 20, 203, 115, 92, 147, 123, 132, 94, 203, 180, 2, 17, 0, 0, 0, 10, 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