Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e0ab3272a317118f12fcf1bf9eb916a692aa7bb5b063d80260c55aea804a9e

Tx prefix hash: 443f6f53fb1bb8d98981b1fc745c9f3bea17763c83a9430f268aa9ed527c2444
Tx public key: f0d3ca5cc3d115d8a48b351dce885e16ffe1c203383179a34ea32f2883a34d54
Timestamp: 1738284707 Timestamp [UCT]: 2025-01-31 00:51:47 Age [y:d:h:m:s]: 00:136:10:43:22
Block: 1208721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97488 RingCT/type: yes/0
Extra: 01f0d3ca5cc3d115d8a48b351dce885e16ffe1c203383179a34ea32f2883a34d54021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4cee615b791671260f56696a819719cb50ec18ed64b401b6f5615ebf32bd872 0.600000000000 1695456 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": 1208731, "vin": [ { "gen": { "height": 1208721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4cee615b791671260f56696a819719cb50ec18ed64b401b6f5615ebf32bd872" } } ], "extra": [ 1, 240, 211, 202, 92, 195, 209, 21, 216, 164, 139, 53, 29, 206, 136, 94, 22, 255, 225, 194, 3, 56, 49, 121, 163, 78, 163, 47, 40, 131, 163, 77, 84, 2, 17, 0, 0, 0, 5, 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