Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990fd22a1fba3d06c6d969bfc381f5e8e08837af27f4cc3d5e772a869c431088

Tx prefix hash: fc2b2a9bd29ee71040d4d0327902049a7e8509040819ddaae51cf8b9fd04e0c7
Tx public key: 3012d2c608514e04172802b029472e1f3ffe6bb121d944b4e49efcec36811053
Timestamp: 1737029998 Timestamp [UCT]: 2025-01-16 12:19:58 Age [y:d:h:m:s]: 00:335:04:22:17
Block: 1198591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237107 RingCT/type: yes/0
Extra: 013012d2c608514e04172802b029472e1f3ffe6bb121d944b4e49efcec36811053021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eb2fd5fc9549a9e2579a015c5c847b41520b4e05f56a6379f1680f1b7fb689e 0.600000000000 1685216 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": 1198601, "vin": [ { "gen": { "height": 1198591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eb2fd5fc9549a9e2579a015c5c847b41520b4e05f56a6379f1680f1b7fb689e" } } ], "extra": [ 1, 48, 18, 210, 198, 8, 81, 78, 4, 23, 40, 2, 176, 41, 71, 46, 31, 63, 254, 107, 177, 33, 217, 68, 180, 228, 158, 252, 236, 54, 129, 16, 83, 2, 17, 0, 0, 0, 4, 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