Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2b13f41a95ac3fc5321c17e4b177100c7bde09ec1469386361a0369f8198a43

Tx prefix hash: cf8b42e407a0500187e018cc03cf6cbc319ac05ab142f7e6a98e07ba4f0725e5
Tx public key: e9f489cb2e120e70a38f37e8af295cd73d1d426a87306cb1bbd550a9adae8119
Timestamp: 1743312124 Timestamp [UCT]: 2025-03-30 05:22:04 Age [y:d:h:m:s]: 00:233:02:48:32
Block: 1250340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164335 RingCT/type: yes/0
Extra: 01e9f489cb2e120e70a38f37e8af295cd73d1d426a87306cb1bbd550a9adae811902110000000c9ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d67c373e23bee3eef9f068b36fecce60c91b41d93565060447694e421aaab18b 0.600000000000 1737389 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": 1250350, "vin": [ { "gen": { "height": 1250340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d67c373e23bee3eef9f068b36fecce60c91b41d93565060447694e421aaab18b" } } ], "extra": [ 1, 233, 244, 137, 203, 46, 18, 14, 112, 163, 143, 55, 232, 175, 41, 92, 215, 61, 29, 66, 106, 135, 48, 108, 177, 187, 213, 80, 169, 173, 174, 129, 25, 2, 17, 0, 0, 0, 12, 155, 166, 41, 223, 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