Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ddc4cb235783117cd506842a63579306eb4945a57c2cef890732ab2f6c7a47

Tx prefix hash: 3a047a104690c1aa9f2c960a51194b283a52759cac003877875bfcf591e9c3dc
Tx public key: bee9cbdee6fc76b4f5a01bd7aadc8bc5f732f6b0e3ac3a22e69da087d1c586e2
Timestamp: 1697130002 Timestamp [UCT]: 2023-10-12 17:00:02 Age [y:d:h:m:s]: 01:165:09:03:05
Block: 868166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379200 RingCT/type: yes/0
Extra: 01bee9cbdee6fc76b4f5a01bd7aadc8bc5f732f6b0e3ac3a22e69da087d1c586e20211000000014b8f5122000000000000000000

1 output(s) for total of 0.815465664000 dcy

stealth address amount amount idx
00: b5284a7bf60f55e66d67eb942b53b5fc9f823ba147108fd626c16a105c4d4de7 0.815465664000 1322941 of 0

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": 868176, "vin": [ { "gen": { "height": 868166 } } ], "vout": [ { "amount": 815465664, "target": { "key": "b5284a7bf60f55e66d67eb942b53b5fc9f823ba147108fd626c16a105c4d4de7" } } ], "extra": [ 1, 190, 233, 203, 222, 230, 252, 118, 180, 245, 160, 27, 215, 170, 220, 139, 197, 247, 50, 246, 176, 227, 172, 58, 34, 230, 157, 160, 135, 209, 197, 134, 226, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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