Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ac094cc1057da9f3a66e8a6e7350b390404901fb3b062204a145689724e62e6

Tx prefix hash: ea9b9cf393330d321ecca2872ea7313a217c2d9aa7b734064af91aa5f4bfcd8d
Tx public key: 8ca6a7a15b4e3c5280182475e537143618482f5485d42af5f1bdd73e7968c216
Timestamp: 1742388022 Timestamp [UCT]: 2025-03-19 12:40:22 Age [y:d:h:m:s]: 00:089:06:09:08
Block: 1242709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63716 RingCT/type: yes/0
Extra: 018ca6a7a15b4e3c5280182475e537143618482f5485d42af5f1bdd73e7968c2160211000000081db82ba9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d1e5343eede3cec7ff8395186f184591aef2e339d05ef5f29b15685cfad81f3 0.600000000000 1729684 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": 1242719, "vin": [ { "gen": { "height": 1242709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d1e5343eede3cec7ff8395186f184591aef2e339d05ef5f29b15685cfad81f3" } } ], "extra": [ 1, 140, 166, 167, 161, 91, 78, 60, 82, 128, 24, 36, 117, 229, 55, 20, 54, 24, 72, 47, 84, 133, 212, 42, 245, 241, 189, 215, 62, 121, 104, 194, 22, 2, 17, 0, 0, 0, 8, 29, 184, 43, 169, 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