Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cd6a7026d19ccdec4431d2e8a3247edf445fdc43ff69e35979612204c4c7bb6

Tx prefix hash: 2446fc54a8ff7ffeecab6f41b698a26308f9e385371dbb62e73040136c8458e8
Tx public key: d4408552e5589f041ae0e9925b75e5f253ca15efb9cc204e6b8e0e6660c85c20
Timestamp: 1719564365 Timestamp [UCT]: 2024-06-28 08:46:05 Age [y:d:h:m:s]: 00:276:11:03:46
Block: 1053943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197537 RingCT/type: yes/0
Extra: 01d4408552e5589f041ae0e9925b75e5f253ca15efb9cc204e6b8e0e6660c85c200211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea0588b87dcb391ff95cac9071c911c3d983fca3c2c142a71cf5167805c8fe53 0.600000000000 1524298 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": 1053953, "vin": [ { "gen": { "height": 1053943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea0588b87dcb391ff95cac9071c911c3d983fca3c2c142a71cf5167805c8fe53" } } ], "extra": [ 1, 212, 64, 133, 82, 229, 88, 159, 4, 26, 224, 233, 146, 91, 117, 229, 242, 83, 202, 21, 239, 185, 204, 32, 78, 107, 142, 14, 102, 96, 200, 92, 32, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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