Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f13a8716f0b5eb1aa41c3d0360495f03812b36b22b0bb310976c0e4abd8469ee

Tx prefix hash: 895cbe31a52564fa3b0599e70ef28a0ff76f8408e24d63401a0afa77b3585049
Tx public key: 172957dfb1653e2b655f5e55bf06d71d471f17b1e5f453df1683f650f879e1d6
Timestamp: 1699075374 Timestamp [UCT]: 2023-11-04 05:22:54 Age [y:d:h:m:s]: 01:079:22:56:04
Block: 884286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318322 RingCT/type: yes/0
Extra: 01172957dfb1653e2b655f5e55bf06d71d471f17b1e5f453df1683f650f879e1d602110000000333af99f4000000000000000000

1 output(s) for total of 0.721096527000 dcy

stealth address amount amount idx
00: b35e925848a07db68a4c010be7197ef8dd02595ccc67e05694db46bf3ff28a74 0.721096527000 1340023 of 0

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": 884296, "vin": [ { "gen": { "height": 884286 } } ], "vout": [ { "amount": 721096527, "target": { "key": "b35e925848a07db68a4c010be7197ef8dd02595ccc67e05694db46bf3ff28a74" } } ], "extra": [ 1, 23, 41, 87, 223, 177, 101, 62, 43, 101, 95, 94, 85, 191, 6, 215, 29, 71, 31, 23, 177, 229, 244, 83, 223, 22, 131, 246, 80, 248, 121, 225, 214, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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