Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a629b963bcbfa5a2c22704d9308e69d5363ad960549c337c69f94581a1841b

Tx prefix hash: d480718106484afe0f3024bae1c710008519310fc7d7f249e26aeda3a068e385
Tx public key: f857f288f25fa66a9580a78d8e484b152cb381d77db593c4d142ec191a6222c2
Timestamp: 1588515074 Timestamp [UCT]: 2020-05-03 14:11:14 Age [y:d:h:m:s]: 04:282:01:36:32
Block: 98087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116800 RingCT/type: yes/0
Extra: 01f857f288f25fa66a9580a78d8e484b152cb381d77db593c4d142ec191a6222c20211000001a8a86a1a65000000000000000000

1 output(s) for total of 290.400804967000 dcy

stealth address amount amount idx
00: fd9967a90722a148a2ce08c4c989a9d3cfe49ffdf30e135dd6b6c1d85bd957ed 290.400804967000 173448 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": 98097, "vin": [ { "gen": { "height": 98087 } } ], "vout": [ { "amount": 290400804967, "target": { "key": "fd9967a90722a148a2ce08c4c989a9d3cfe49ffdf30e135dd6b6c1d85bd957ed" } } ], "extra": [ 1, 248, 87, 242, 136, 242, 95, 166, 106, 149, 128, 167, 141, 142, 72, 75, 21, 44, 179, 129, 215, 125, 181, 147, 196, 209, 66, 236, 25, 26, 98, 34, 194, 2, 17, 0, 0, 1, 168, 168, 106, 26, 101, 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