Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 900a8c5718bbe0c37df8fcc22876af5339c7f615c25f13dab767c51e86964ad3

Tx prefix hash: 4090780e367fbce276279112fb22c95c47a519a0b005e2eca6379ea12f18f702
Tx public key: 0fb219c4bd8fbf30ca2b8a5eacb0a3ba2e42d51009b05c2828c85b22c97940a7
Timestamp: 1732619397 Timestamp [UCT]: 2024-11-26 11:09:57 Age [y:d:h:m:s]: 00:118:22:45:11
Block: 1162081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84813 RingCT/type: yes/0
Extra: 010fb219c4bd8fbf30ca2b8a5eacb0a3ba2e42d51009b05c2828c85b22c97940a7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d92d6fa7839d6539a0852bc30849761d0d9fee2b86ad37cf5d65009bb0001c96 0.600000000000 1647736 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": 1162091, "vin": [ { "gen": { "height": 1162081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d92d6fa7839d6539a0852bc30849761d0d9fee2b86ad37cf5d65009bb0001c96" } } ], "extra": [ 1, 15, 178, 25, 196, 189, 143, 191, 48, 202, 43, 138, 94, 172, 176, 163, 186, 46, 66, 213, 16, 9, 176, 92, 40, 40, 200, 91, 34, 201, 121, 64, 167, 2, 17, 0, 0, 0, 2, 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