Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 831c41809b476b7b113d5ab6f6b09827c4cd69719c3832fb05a4f329a44954eb

Tx prefix hash: 3e6f8bc00d5ff328287bc5c7da5ede5ce9f1885092d42a2de707b849fb4a35f4
Tx public key: ce807ae0f2610ca78791643f7c81906d99c8b3ad65ae0056772301e6f60491b8
Timestamp: 1744561869 Timestamp [UCT]: 2025-04-13 16:31:09 Age [y:d:h:m:s]: 00:221:11:29:31
Block: 1260694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155996 RingCT/type: yes/0
Extra: 01ce807ae0f2610ca78791643f7c81906d99c8b3ad65ae0056772301e6f60491b8021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c7c311c177235c67a065fce6065f4f91227f9496ebda950946ccca1452c70b5 0.600000000000 1747855 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": 1260704, "vin": [ { "gen": { "height": 1260694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c7c311c177235c67a065fce6065f4f91227f9496ebda950946ccca1452c70b5" } } ], "extra": [ 1, 206, 128, 122, 224, 242, 97, 12, 167, 135, 145, 100, 63, 124, 129, 144, 109, 153, 200, 179, 173, 101, 174, 0, 86, 119, 35, 1, 230, 246, 4, 145, 184, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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