Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01072dc2d1473072bbc922bf0558cd5a3a4e0046b884c5253658dd771b346718

Tx prefix hash: 4991d148c30d74c4f1d390a4de988b0122b61d417b706566dd28bf3389fc9061
Tx public key: 2762b8e958f006be3e143078eb21af4f5f7c84d9a7b3c15df290f685985bd1d0
Timestamp: 1727166071 Timestamp [UCT]: 2024-09-24 08:21:11 Age [y:d:h:m:s]: 00:061:10:03:20
Block: 1116972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43888 RingCT/type: yes/0
Extra: 012762b8e958f006be3e143078eb21af4f5f7c84d9a7b3c15df290f685985bd1d002110000001591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b01ccb67baaf69f38e73e0cbc5a0d14c8962d9156c9a7fffeeae43cc6c58bef4 0.600000000000 1597639 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": 1116982, "vin": [ { "gen": { "height": 1116972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b01ccb67baaf69f38e73e0cbc5a0d14c8962d9156c9a7fffeeae43cc6c58bef4" } } ], "extra": [ 1, 39, 98, 184, 233, 88, 240, 6, 190, 62, 20, 48, 120, 235, 33, 175, 79, 95, 124, 132, 217, 167, 179, 193, 93, 242, 144, 246, 133, 152, 91, 209, 208, 2, 17, 0, 0, 0, 21, 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