Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a107c67e69d425dfb26294e00a2225125c34a219d23ce84e4b2a3d53c64564f5

Tx prefix hash: 49528a817e67b779897acdfef8b4e73be3c4856fd323a0b9b6fe48aa785e9b21
Tx public key: 68f23ff4f936133670d1f3361c38260f6f6af5ed5917fbce986e1671cc51c96b
Timestamp: 1702936118 Timestamp [UCT]: 2023-12-18 21:48:38 Age [y:d:h:m:s]: 01:180:04:58:18
Block: 916086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389870 RingCT/type: yes/0
Extra: 0168f23ff4f936133670d1f3361c38260f6f6af5ed5917fbce986e1671cc51c96b02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8a3ccad77ea2698e307c29ce9aa703a2874e1ee573f95a645254548e394d643 0.600000000000 1373560 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": 916096, "vin": [ { "gen": { "height": 916086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8a3ccad77ea2698e307c29ce9aa703a2874e1ee573f95a645254548e394d643" } } ], "extra": [ 1, 104, 242, 63, 244, 249, 54, 19, 54, 112, 209, 243, 54, 28, 56, 38, 15, 111, 106, 245, 237, 89, 23, 251, 206, 152, 110, 22, 113, 204, 81, 201, 107, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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