Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 103007a2aeb13dd37fa2311fd24d21e141da195bb893a67436f3a5e746cb8df4

Tx prefix hash: 75aa91a6ad51d016e201ed3ef6f87bd3a2a7e32827fbebf89a37d903ef5c3033
Tx public key: 811fb83d0014ca5b80ed1699074bc53d8fceccdc0af8196dd7e1655bd36681f4
Timestamp: 1717392516 Timestamp [UCT]: 2024-06-03 05:28:36 Age [y:d:h:m:s]: 00:289:17:58:34
Block: 1035952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207082 RingCT/type: yes/0
Extra: 01811fb83d0014ca5b80ed1699074bc53d8fceccdc0af8196dd7e1655bd36681f4021100000003162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4843f7e7ae401f0963eab7a4a7f47fa50cd2fb22a8b1aed100b245d394714dda 0.600000000000 1504477 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": 1035962, "vin": [ { "gen": { "height": 1035952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4843f7e7ae401f0963eab7a4a7f47fa50cd2fb22a8b1aed100b245d394714dda" } } ], "extra": [ 1, 129, 31, 184, 61, 0, 20, 202, 91, 128, 237, 22, 153, 7, 75, 197, 61, 143, 206, 204, 220, 10, 248, 25, 109, 215, 225, 101, 91, 211, 102, 129, 244, 2, 17, 0, 0, 0, 3, 22, 38, 19, 170, 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