Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c87118287b8dc9635e5a2701e511ef281d1e5b3d4031fe3d2075ae77a7dd3a44

Tx prefix hash: 8220a984772aafd19e3b978b4f62ea12aff04aaae5f22cc8a882674deed27dba
Tx public key: 584b49190beba5afdc3d16a6c3834cc1e257635bf889fa19dbedcb5f81c10c53
Timestamp: 1728736240 Timestamp [UCT]: 2024-10-12 12:30:40 Age [y:d:h:m:s]: 00:194:07:00:02
Block: 1129982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138658 RingCT/type: yes/0
Extra: 01584b49190beba5afdc3d16a6c3834cc1e257635bf889fa19dbedcb5f81c10c53021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fc5c6c4f58a636a09cc225f6eeff3b2aceb09a0802712e4b528c4706af3b3f2 0.600000000000 1612853 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": 1129992, "vin": [ { "gen": { "height": 1129982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fc5c6c4f58a636a09cc225f6eeff3b2aceb09a0802712e4b528c4706af3b3f2" } } ], "extra": [ 1, 88, 75, 73, 25, 11, 235, 165, 175, 220, 61, 22, 166, 195, 131, 76, 193, 226, 87, 99, 91, 248, 137, 250, 25, 219, 237, 203, 95, 129, 193, 12, 83, 2, 17, 0, 0, 0, 1, 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