Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45901a1d3ad6b0f1cab7277dd40f06aae20ddb185eb10e1e33cb9f003ee645e0

Tx prefix hash: 1a08f6925257fe4fe3443c0d1ed7dc6b9e4b0a110316f12ff46b9c015f526e99
Tx public key: 49f4f318cdbead98407bf7432ac035baeccd0fd56da4a3f3da13c4209de6dfea
Timestamp: 1582096828 Timestamp [UCT]: 2020-02-19 07:20:28 Age [y:d:h:m:s]: 05:051:09:06:41
Block: 67853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1189958 RingCT/type: yes/0
Extra: 0149f4f318cdbead98407bf7432ac035baeccd0fd56da4a3f3da13c4209de6dfea0211000000020aca7173000000000000000000

1 output(s) for total of 365.742686587000 dcy

stealth address amount amount idx
00: d1d0d1fa7bd5700691326feac19c5c2c0e389f017bb4e8270632f9b69d1181cb 365.742686587000 125045 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": 67863, "vin": [ { "gen": { "height": 67853 } } ], "vout": [ { "amount": 365742686587, "target": { "key": "d1d0d1fa7bd5700691326feac19c5c2c0e389f017bb4e8270632f9b69d1181cb" } } ], "extra": [ 1, 73, 244, 243, 24, 205, 190, 173, 152, 64, 123, 247, 67, 42, 192, 53, 186, 236, 205, 15, 213, 109, 164, 163, 243, 218, 19, 196, 32, 157, 230, 223, 234, 2, 17, 0, 0, 0, 2, 10, 202, 113, 115, 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