Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d4cea386b320f2da01a7a50a7dc09eb7906de5e41aa88962f5f187ef41d549c

Tx prefix hash: 72b52057ec1a6a5e060531a65e4db273443ac51006627ffc5538c1ef610f50f0
Tx public key: ea340f0b1cb2373554ce94cc02c03375cd8fbcca22b862d79eb62cd57f95dafb
Timestamp: 1583082366 Timestamp [UCT]: 2020-03-01 17:06:06 Age [y:d:h:m:s]: 04:261:00:46:36
Block: 74697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080414 RingCT/type: yes/0
Extra: 01ea340f0b1cb2373554ce94cc02c03375cd8fbcca22b862d79eb62cd57f95dafb0211000001410aca7173000000000000000000

1 output(s) for total of 347.135179648000 dcy

stealth address amount amount idx
00: c75ab88742f215ad079845a9f35e59d3d83c4d1dd0f3af21856c5e4b26ab4ac2 347.135179648000 138171 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": 74707, "vin": [ { "gen": { "height": 74697 } } ], "vout": [ { "amount": 347135179648, "target": { "key": "c75ab88742f215ad079845a9f35e59d3d83c4d1dd0f3af21856c5e4b26ab4ac2" } } ], "extra": [ 1, 234, 52, 15, 11, 28, 178, 55, 53, 84, 206, 148, 204, 2, 192, 51, 117, 205, 143, 188, 202, 34, 184, 98, 215, 158, 182, 44, 213, 127, 149, 218, 251, 2, 17, 0, 0, 1, 65, 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