Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff68871e3c2aaa7f3fd7ba486042f8b79328e54e4efcc5354537f8f398d227df

Tx prefix hash: 7d1c47c4fb68ec80ba353fd830267d8d94fe3f6ab10979e5435bdae4d044da2d
Tx public key: 89741fae0ee8d22ada820ea0e05716c12bfd73b138b5c6cb5f1c16b3e5ec1eeb
Timestamp: 1723175212 Timestamp [UCT]: 2024-08-09 03:46:52 Age [y:d:h:m:s]: 00:284:20:50:32
Block: 1083877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203524 RingCT/type: yes/0
Extra: 0189741fae0ee8d22ada820ea0e05716c12bfd73b138b5c6cb5f1c16b3e5ec1eeb02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beffc86d7b48ae0ee4293c7790480d1587d7036fbd7814adb188a4f75056e17e 0.600000000000 1557952 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": 1083887, "vin": [ { "gen": { "height": 1083877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beffc86d7b48ae0ee4293c7790480d1587d7036fbd7814adb188a4f75056e17e" } } ], "extra": [ 1, 137, 116, 31, 174, 14, 232, 210, 42, 218, 130, 14, 160, 224, 87, 22, 193, 43, 253, 115, 177, 56, 181, 198, 203, 95, 28, 22, 179, 229, 236, 30, 235, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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