Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e9d04578f520aa765ed8a347f8493c8c66dd267f6c5464d6631b042f23cf42e

Tx prefix hash: a3c4fa52db60c6c9513e33ffa453e3a9453671c484428338df65e221deeab5d3
Tx public key: 8fbb5da9619433cf632e09bda5637d04167a6d04e0d04a01fe2ac5202ca12de0
Timestamp: 1574660726 Timestamp [UCT]: 2019-11-25 05:45:26 Age [y:d:h:m:s]: 05:002:07:48:35
Block: 16949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144487 RingCT/type: yes/0
Extra: 018fbb5da9619433cf632e09bda5637d04167a6d04e0d04a01fe2ac5202ca12de0021100000001f95225a5000000000000000000

1 output(s) for total of 539.326091806000 dcy

stealth address amount amount idx
00: 9c3e44e1da30d85e4a2fcaeb0da4cb2339e8537ab9eb2fd1d8570ff5fae8e299 539.326091806000 24153 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": 16959, "vin": [ { "gen": { "height": 16949 } } ], "vout": [ { "amount": 539326091806, "target": { "key": "9c3e44e1da30d85e4a2fcaeb0da4cb2339e8537ab9eb2fd1d8570ff5fae8e299" } } ], "extra": [ 1, 143, 187, 93, 169, 97, 148, 51, 207, 99, 46, 9, 189, 165, 99, 125, 4, 22, 122, 109, 4, 224, 208, 74, 1, 254, 42, 197, 32, 44, 161, 45, 224, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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