Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce3d7eab5446a09cf300c016e22640c99aaafe1a7b4d9a74cd1ac2f8ebdd9fbc

Tx prefix hash: 45c3707f260bc89b6eecd5ba0ec2de3626e8864a44751c8de51239cc1b5e5c6f
Tx public key: e50924043dbef2830710f7df2ca85c355831ed140257e6d2a3d710e380398635
Timestamp: 1738102153 Timestamp [UCT]: 2025-01-28 22:09:13 Age [y:d:h:m:s]: 00:322:23:18:33
Block: 1207212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228626 RingCT/type: yes/0
Extra: 01e50924043dbef2830710f7df2ca85c355831ed140257e6d2a3d710e38039863502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50e772de66165525e18aac1ae5d9c51c9d20a2590346aaf4f1ed83a5911a058c 0.600000000000 1693933 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": 1207222, "vin": [ { "gen": { "height": 1207212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50e772de66165525e18aac1ae5d9c51c9d20a2590346aaf4f1ed83a5911a058c" } } ], "extra": [ 1, 229, 9, 36, 4, 61, 190, 242, 131, 7, 16, 247, 223, 44, 168, 92, 53, 88, 49, 237, 20, 2, 87, 230, 210, 163, 215, 16, 227, 128, 57, 134, 53, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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