Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bdbf298403d25f1786d95db68ce64ed906f33fce9ac19173d6e5b4417119a56

Tx prefix hash: 19bf65c87ed6dc1cd731bab466ce9157584c136e6891dbc97c136f18d2c19780
Tx public key: fae22d28dc8ffe2a7d40e5b6b43319d95a35bdda7d46b5fa758726ae8a645450
Timestamp: 1578995987 Timestamp [UCT]: 2020-01-14 09:59:47 Age [y:d:h:m:s]: 05:094:01:47:56
Block: 45218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1217471 RingCT/type: yes/0
Extra: 01fae22d28dc8ffe2a7d40e5b6b43319d95a35bdda7d46b5fa758726ae8a64545002110000000e8a2ee0d9000000000000000000

1 output(s) for total of 434.685181341000 dcy

stealth address amount amount idx
00: 2fe034784bf39d1a5802d519192b8cf0c4317842075ba03a1ab7f38649ee0e14 434.685181341000 82550 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": 45228, "vin": [ { "gen": { "height": 45218 } } ], "vout": [ { "amount": 434685181341, "target": { "key": "2fe034784bf39d1a5802d519192b8cf0c4317842075ba03a1ab7f38649ee0e14" } } ], "extra": [ 1, 250, 226, 45, 40, 220, 143, 254, 42, 125, 64, 229, 182, 180, 51, 25, 217, 90, 53, 189, 218, 125, 70, 181, 250, 117, 135, 38, 174, 138, 100, 84, 80, 2, 17, 0, 0, 0, 14, 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