Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab2e424d20ba439a9f1913d22dd6444a70f384c3aaaf3f6b79b4d178b52a853d

Tx prefix hash: b153f1a102ccde737fea2f54a3b37d89347519bac01e45fb1e3a9621f4b7a92e
Tx public key: c2080355fc13b32c4d261bc31586cd694031482db2325dee017ba64969d648e8
Timestamp: 1727307593 Timestamp [UCT]: 2024-09-25 23:39:53 Age [y:d:h:m:s]: 00:059:18:54:13
Block: 1118136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42730 RingCT/type: yes/0
Extra: 01c2080355fc13b32c4d261bc31586cd694031482db2325dee017ba64969d648e8021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bec68afd714d34b6b182a58acf7e846740d4f0b2b0c1ed048e5b2f01af10793 0.600000000000 1599227 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": 1118146, "vin": [ { "gen": { "height": 1118136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bec68afd714d34b6b182a58acf7e846740d4f0b2b0c1ed048e5b2f01af10793" } } ], "extra": [ 1, 194, 8, 3, 85, 252, 19, 179, 44, 77, 38, 27, 195, 21, 134, 205, 105, 64, 49, 72, 45, 178, 50, 93, 238, 1, 123, 166, 73, 105, 214, 72, 232, 2, 17, 0, 0, 0, 5, 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