Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd34f07574bc3eeda47f827c7aa63b587fa4a4000dcb5f9e42803cbccc0f587

Tx prefix hash: db5ef30e7e2cd3e7acb598f8aa2287a09eb9b0512738df6616711da2dbe0c23b
Tx public key: e06e40e88ad1af2bb35aa4bd7c32ee1265a5512b450843393bf69cb7775a013d
Timestamp: 1704089061 Timestamp [UCT]: 2024-01-01 06:04:21 Age [y:d:h:m:s]: 01:167:22:29:00
Block: 925639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381068 RingCT/type: yes/0
Extra: 01e06e40e88ad1af2bb35aa4bd7c32ee1265a5512b450843393bf69cb7775a013d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c868b50cc034784cde90ea0ed41f59de9bf6037f5fdb41adb57917ab4e2b7ab 0.600000000000 1383403 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": 925649, "vin": [ { "gen": { "height": 925639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c868b50cc034784cde90ea0ed41f59de9bf6037f5fdb41adb57917ab4e2b7ab" } } ], "extra": [ 1, 224, 110, 64, 232, 138, 209, 175, 43, 179, 90, 164, 189, 124, 50, 238, 18, 101, 165, 81, 43, 69, 8, 67, 57, 59, 246, 156, 183, 119, 90, 1, 61, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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