Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d65f72d597d18d3837dd4e06df4c0ed0061355ee617f89929f74e54116e7c0c

Tx prefix hash: 25e9bac4bb94bab44a4a749f0b4f384c41c7874483990872a4cba19b16f2e0b3
Tx public key: 653f219061dc270df6eef854cffb8e7a592bf2dc4cefc2018df885f4e8a87be4
Timestamp: 1720386233 Timestamp [UCT]: 2024-07-07 21:03:53 Age [y:d:h:m:s]: 00:282:19:10:12
Block: 1060752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202064 RingCT/type: yes/0
Extra: 01653f219061dc270df6eef854cffb8e7a592bf2dc4cefc2018df885f4e8a87be4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 995213cf852b88abf2f42c4b24429d14cefca26ad3fac618fce3bb637f41f90f 0.600000000000 1531237 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": 1060762, "vin": [ { "gen": { "height": 1060752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "995213cf852b88abf2f42c4b24429d14cefca26ad3fac618fce3bb637f41f90f" } } ], "extra": [ 1, 101, 63, 33, 144, 97, 220, 39, 13, 246, 238, 248, 84, 207, 251, 142, 122, 89, 43, 242, 220, 76, 239, 194, 1, 141, 248, 133, 244, 232, 168, 123, 228, 2, 17, 0, 0, 0, 4, 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