Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ff1ccb91f8d5ac985cfaa66be35c01207612b27bffcd8a83acd4e8c88962601

Tx prefix hash: 8c31f06e1b93cac1eba02e11c89fb1bd8dd686c5824817ec9cafd10e2d543e4b
Tx public key: 130e6e6d955c1192b2c571b95706a362e3fc9d278fe2211976976fcfe7262fa7
Timestamp: 1722514484 Timestamp [UCT]: 2024-08-01 12:14:44 Age [y:d:h:m:s]: 00:300:19:34:35
Block: 1078403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214943 RingCT/type: yes/0
Extra: 01130e6e6d955c1192b2c571b95706a362e3fc9d278fe2211976976fcfe7262fa7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81efc85376ed548663f0c96e6c2d08938a8e1eea3c9df1c0dd3117b48dda8f11 0.600000000000 1550980 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": 1078413, "vin": [ { "gen": { "height": 1078403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81efc85376ed548663f0c96e6c2d08938a8e1eea3c9df1c0dd3117b48dda8f11" } } ], "extra": [ 1, 19, 14, 110, 109, 149, 92, 17, 146, 178, 197, 113, 185, 87, 6, 163, 98, 227, 252, 157, 39, 143, 226, 33, 25, 118, 151, 111, 207, 231, 38, 47, 167, 2, 17, 0, 0, 0, 6, 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