Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e28f36c09a9c0fafc5633b191beef2b182f4dd73ebf65058dd31353baf15cba

Tx prefix hash: ff6d9300e5f55475e3dcfef5a9cffe25e2ec1ae6d255341eb626527d1382856d
Tx public key: 53f4462e82e2424911d62ae969f649a1dc1f08ee210c1aec8815494ffc931e61
Timestamp: 1724370419 Timestamp [UCT]: 2024-08-22 23:46:59 Age [y:d:h:m:s]: 00:204:01:08:40
Block: 1093801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145696 RingCT/type: yes/0
Extra: 0153f4462e82e2424911d62ae969f649a1dc1f08ee210c1aec8815494ffc931e61021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f228c85cd0014fcb4a7d0af955550fdb09c527dfa68bfb8b730b6eb26bde8b0e 0.600000000000 1568818 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": 1093811, "vin": [ { "gen": { "height": 1093801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f228c85cd0014fcb4a7d0af955550fdb09c527dfa68bfb8b730b6eb26bde8b0e" } } ], "extra": [ 1, 83, 244, 70, 46, 130, 226, 66, 73, 17, 214, 42, 233, 105, 246, 73, 161, 220, 31, 8, 238, 33, 12, 26, 236, 136, 21, 73, 79, 252, 147, 30, 97, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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