Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3478c891c9fcb166f7f6ee8e8828a17afb9dc78d36f9946ae828e64503a553de

Tx prefix hash: bfdaa3a484f7e7dd39d555c5eeb2bcbd11068dd0bdf0ed612c39e7ac9cb4fd3c
Tx public key: 33140b071c1ec4db7515b08c024b61509313987c8ef466ea33e801446d313d9f
Timestamp: 1574436318 Timestamp [UCT]: 2019-11-22 15:25:18 Age [y:d:h:m:s]: 05:008:21:17:36
Block: 14544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1149737 RingCT/type: yes/0
Extra: 0133140b071c1ec4db7515b08c024b61509313987c8ef466ea33e801446d313d9f02110000000166a80d00000000000000000000

1 output(s) for total of 549.301234836000 dcy

stealth address amount amount idx
00: b98b84cb864de735462606b270e63d44894f27de03c2cfc64a7b318635b89fef 549.301234836000 18555 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": 14554, "vin": [ { "gen": { "height": 14544 } } ], "vout": [ { "amount": 549301234836, "target": { "key": "b98b84cb864de735462606b270e63d44894f27de03c2cfc64a7b318635b89fef" } } ], "extra": [ 1, 51, 20, 11, 7, 28, 30, 196, 219, 117, 21, 176, 140, 2, 75, 97, 80, 147, 19, 152, 124, 142, 244, 102, 234, 51, 232, 1, 68, 109, 49, 61, 159, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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