Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fa47732a5106c9e3ff78a4292bb40e09716d7f3f65c122f2195d6cdf15407f8

Tx prefix hash: 51c1b9115b8e2bd4e0613d47fa6d1607f991d6a35b6943a9a84047eef2e7cb45
Tx public key: 591e4d3a3f0889c25822c86e87f676a4304aed143705356b1947e83426576559
Timestamp: 1579016975 Timestamp [UCT]: 2020-01-14 15:49:35 Age [y:d:h:m:s]: 04:357:12:30:13
Block: 45403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145099 RingCT/type: yes/0
Extra: 01591e4d3a3f0889c25822c86e87f676a4304aed143705356b1947e834265765590211000000114ac5aa02000000000000000000

1 output(s) for total of 434.096920603000 dcy

stealth address amount amount idx
00: 47f0ec3068cd0249e0f86896484387ca7116f852e4f1f3d9b4a750445a4084e1 434.096920603000 82942 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": 45413, "vin": [ { "gen": { "height": 45403 } } ], "vout": [ { "amount": 434096920603, "target": { "key": "47f0ec3068cd0249e0f86896484387ca7116f852e4f1f3d9b4a750445a4084e1" } } ], "extra": [ 1, 89, 30, 77, 58, 63, 8, 137, 194, 88, 34, 200, 110, 135, 246, 118, 164, 48, 74, 237, 20, 55, 5, 53, 107, 25, 71, 232, 52, 38, 87, 101, 89, 2, 17, 0, 0, 0, 17, 74, 197, 170, 2, 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