Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91858b785c87b0d538f15699d3524f9aebfd3021ce8a75a2c082cd1463f4a7d9

Tx prefix hash: c1c6be5c2ed780438673bbafab4ba2504f8d52450eaed14a77cdd254cd924fc2
Tx public key: 4a902ff2d62e7110467500772b4c94ae9c81aa52cc418c4370989d72cb519395
Timestamp: 1741398375 Timestamp [UCT]: 2025-03-08 01:46:15 Age [y:d:h:m:s]: 00:258:07:50:59
Block: 1234496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182362 RingCT/type: yes/0
Extra: 014a902ff2d62e7110467500772b4c94ae9c81aa52cc418c4370989d72cb519395021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eee9a3698b84bef426d66b51928a53856e9d0123e2b06219a20dc325199e94c7 0.600000000000 1721423 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": 1234506, "vin": [ { "gen": { "height": 1234496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eee9a3698b84bef426d66b51928a53856e9d0123e2b06219a20dc325199e94c7" } } ], "extra": [ 1, 74, 144, 47, 242, 214, 46, 113, 16, 70, 117, 0, 119, 43, 76, 148, 174, 156, 129, 170, 82, 204, 65, 140, 67, 112, 152, 157, 114, 203, 81, 147, 149, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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