Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2fa51e960d9da9dab7f37ff3dfa6bae316837a0e49cd8d03e4f1dac110b93c

Tx prefix hash: 947ff58b02bba013a3d8ca5e47b8d3d0eeb52f630ee6e2c5e57dc29091fdb1d3
Tx public key: 5c40dfb9bf415de7643d3dbe5569e9487a4cc2ebce881c2121784410600324f2
Timestamp: 1578323931 Timestamp [UCT]: 2020-01-06 15:18:51 Age [y:d:h:m:s]: 04:329:01:26:30
Block: 39763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124633 RingCT/type: yes/0
Extra: 015c40dfb9bf415de7643d3dbe5569e9487a4cc2ebce881c2121784410600324f20211000000152264afe6000000000000000000

1 output(s) for total of 453.163195597000 dcy

stealth address amount amount idx
00: 035bf25e55fd6b36c9c6f4598eef0bc8b4835808353aa2873edb6cbf81e43fbf 453.163195597000 69054 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": 39773, "vin": [ { "gen": { "height": 39763 } } ], "vout": [ { "amount": 453163195597, "target": { "key": "035bf25e55fd6b36c9c6f4598eef0bc8b4835808353aa2873edb6cbf81e43fbf" } } ], "extra": [ 1, 92, 64, 223, 185, 191, 65, 93, 231, 100, 61, 61, 190, 85, 105, 233, 72, 122, 76, 194, 235, 206, 136, 28, 33, 33, 120, 68, 16, 96, 3, 36, 242, 2, 17, 0, 0, 0, 21, 34, 100, 175, 230, 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