Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eee0ca748481d179fb6892ba225dee40aa2452be827d3c997b59fc959db5859

Tx prefix hash: 5ef5b168e009ea8107b74cd6ce7f6d06d04f37ca6257c0ecf2443e8da2d9a270
Tx public key: a89063c6ecbe8fb0672a2c50bb7c0fe40bf4a84c037faf597d1ed9b9cd7565b1
Timestamp: 1726376195 Timestamp [UCT]: 2024-09-15 04:56:35 Age [y:d:h:m:s]: 01:068:11:11:46
Block: 1110410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307360 RingCT/type: yes/0
Extra: 01a89063c6ecbe8fb0672a2c50bb7c0fe40bf4a84c037faf597d1ed9b9cd7565b1021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 218f7556b9586ccbe4bbec1d1ef7d9a93f1961e08d37d1ffeed645c1fec9977b 0.600000000000 1589007 of 15

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": 1110420, "vin": [ { "gen": { "height": 1110410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "218f7556b9586ccbe4bbec1d1ef7d9a93f1961e08d37d1ffeed645c1fec9977b" } } ], "extra": [ 1, 168, 144, 99, 198, 236, 190, 143, 176, 103, 42, 44, 80, 187, 124, 15, 228, 11, 244, 168, 76, 3, 127, 175, 89, 125, 30, 217, 185, 205, 117, 101, 177, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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