Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed5e9671c1ccf1907c6426b99b3d15e3b3ebdff7034c639ab8b6efcfc39fd9c

Tx prefix hash: 0fc21a61a99abd02ae7d0a21862d74951115480ee3634ad86588e735a944485d
Tx public key: cd396e45aa9235bdc9fa01bc2774724ceea5f0811ca60fef0c0c5912e88a6267
Timestamp: 1713809506 Timestamp [UCT]: 2024-04-22 18:11:46 Age [y:d:h:m:s]: 00:363:07:00:00
Block: 1006232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259698 RingCT/type: yes/0
Extra: 01cd396e45aa9235bdc9fa01bc2774724ceea5f0811ca60fef0c0c5912e88a626702110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f79015f94cf54f818ae0f8c1ce9bf7bba6a14f564fb3eb64d0b848f0255b80b 0.600000000000 1467186 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": 1006242, "vin": [ { "gen": { "height": 1006232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f79015f94cf54f818ae0f8c1ce9bf7bba6a14f564fb3eb64d0b848f0255b80b" } } ], "extra": [ 1, 205, 57, 110, 69, 170, 146, 53, 189, 201, 250, 1, 188, 39, 116, 114, 76, 238, 165, 240, 129, 28, 166, 15, 239, 12, 12, 89, 18, 232, 138, 98, 103, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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