Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 252db5ab9e793e8b44c817e5e4ac5572b809fa6010667929138c2e16f473a532

Tx prefix hash: ed4fcb17731eb58a479e5b19bd07a1cb4e5b53d273c2db0a46d9405c6dbe9e66
Tx public key: 5c1748ce4a9ef88062ae03d9938f7fceeaf8a1f591ab2a0eecc87563a872c592
Timestamp: 1764960531 Timestamp [UCT]: 2025-12-05 18:48:51 Age [y:d:h:m:s]: 00:034:09:13:21
Block: 1427161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24633 RingCT/type: yes/0
Extra: 015c1748ce4a9ef88062ae03d9938f7fceeaf8a1f591ab2a0eecc87563a872c592021100000007fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee29e3c0b2e7b1550d284f39cd2430d52a03368b5cd083177f4968cde9f3d851 0.600000000000 1915860 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": 1427171, "vin": [ { "gen": { "height": 1427161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee29e3c0b2e7b1550d284f39cd2430d52a03368b5cd083177f4968cde9f3d851" } } ], "extra": [ 1, 92, 23, 72, 206, 74, 158, 248, 128, 98, 174, 3, 217, 147, 143, 127, 206, 234, 248, 161, 245, 145, 171, 42, 14, 236, 200, 117, 99, 168, 114, 197, 146, 2, 17, 0, 0, 0, 7, 251, 143, 208, 137, 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