Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa7616cca18785f263a2156c60074d1e638700e14b4c5547fb766a8a6bf2f55f

Tx prefix hash: 8037999c613c490bbe1f0d258a8e38fca975b546dc24c127940837c1dcee035e
Tx public key: ac7e18221523e3736c91533ddd5c6d6c5406e5c21e8d1bd6afaee5403d612107
Timestamp: 1724805492 Timestamp [UCT]: 2024-08-28 00:38:12 Age [y:d:h:m:s]: 00:221:11:38:19
Block: 1097388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158153 RingCT/type: yes/0
Extra: 01ac7e18221523e3736c91533ddd5c6d6c5406e5c21e8d1bd6afaee5403d61210702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f12f9eda9f15047d79490c6b874425f90189d284d6bbce44d0db032668ecdca1 0.600000000000 1572783 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": 1097398, "vin": [ { "gen": { "height": 1097388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f12f9eda9f15047d79490c6b874425f90189d284d6bbce44d0db032668ecdca1" } } ], "extra": [ 1, 172, 126, 24, 34, 21, 35, 227, 115, 108, 145, 83, 61, 221, 92, 109, 108, 84, 6, 229, 194, 30, 141, 27, 214, 175, 174, 229, 64, 61, 97, 33, 7, 2, 17, 0, 0, 0, 2, 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