Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3c6d02ef01e00e7a887ce40fd8f7e3921d7af1994c1096edb03001d2b9519a

Tx prefix hash: 8172edada5df3b3e295e749d1d006ee083d9bf0da2bb847a3710e4a78c4ab4c9
Tx public key: 814fd5c1948256f2e4ad64c685ace71b20393bac0dfd397a6b0f7d861996ed67
Timestamp: 1743905994 Timestamp [UCT]: 2025-04-06 02:19:54 Age [y:d:h:m:s]: 00:038:12:30:53
Block: 1255248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27566 RingCT/type: yes/0
Extra: 01814fd5c1948256f2e4ad64c685ace71b20393bac0dfd397a6b0f7d861996ed67021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9ae787e2f6c0d4be43360b268f1c29019d03068bccc2a5a1a741376e6815352 0.600000000000 1742351 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": 1255258, "vin": [ { "gen": { "height": 1255248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9ae787e2f6c0d4be43360b268f1c29019d03068bccc2a5a1a741376e6815352" } } ], "extra": [ 1, 129, 79, 213, 193, 148, 130, 86, 242, 228, 173, 100, 198, 133, 172, 231, 27, 32, 57, 59, 172, 13, 253, 57, 122, 107, 15, 125, 134, 25, 150, 237, 103, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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