Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26f520398a63107fc95fe9aad7b6a2c399a185a96d2c65c8afc8f99c727a09be

Tx prefix hash: 38da0ce9532364f6b43ac3833d6eec1399bc42f42dca689c0754b72e10a6a19f
Tx public key: 6999dc90f16e66fe4a7df137144c3f89d5d369ab51029fbbc8a1e6eb9f51142d
Timestamp: 1711630914 Timestamp [UCT]: 2024-03-28 13:01:54 Age [y:d:h:m:s]: 01:029:00:38:05
Block: 988186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281718 RingCT/type: yes/0
Extra: 016999dc90f16e66fe4a7df137144c3f89d5d369ab51029fbbc8a1e6eb9f51142d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 814571fea1aee1a7adbe5d76cca22449f4073a18fa36a2fa29514c5069f90429 0.600000000000 1448453 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": 988196, "vin": [ { "gen": { "height": 988186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "814571fea1aee1a7adbe5d76cca22449f4073a18fa36a2fa29514c5069f90429" } } ], "extra": [ 1, 105, 153, 220, 144, 241, 110, 102, 254, 74, 125, 241, 55, 20, 76, 63, 137, 213, 211, 105, 171, 81, 2, 159, 187, 200, 161, 230, 235, 159, 81, 20, 45, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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