Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fba9bfc9f2f5a6219a6088f25fcad9c7ff1d2e5d6011aa1a5f91bed3e4f51eed

Tx prefix hash: fb5d771601472b83be39f1d8bae3f484b678eb13abb5e4e4fd3c69168d8bf55c
Tx public key: ce43229d65855bbd2323649ab30cec3d2cf5a53e8bb28d8e42b5f035d93ef044
Timestamp: 1683366409 Timestamp [UCT]: 2023-05-06 09:46:49 Age [y:d:h:m:s]: 01:250:20:44:17
Block: 754104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440751 RingCT/type: yes/0
Extra: 01ce43229d65855bbd2323649ab30cec3d2cf5a53e8bb28d8e42b5f035d93ef044021100000002faf35c9c000000000000000000

1 output(s) for total of 1.946886357000 dcy

stealth address amount amount idx
00: 0a07400f26d8af68560b16c7d595bf50a9373de066e32f361653be16ee53bcb6 1.946886357000 1202355 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": 754114, "vin": [ { "gen": { "height": 754104 } } ], "vout": [ { "amount": 1946886357, "target": { "key": "0a07400f26d8af68560b16c7d595bf50a9373de066e32f361653be16ee53bcb6" } } ], "extra": [ 1, 206, 67, 34, 157, 101, 133, 91, 189, 35, 35, 100, 154, 179, 12, 236, 61, 44, 245, 165, 62, 139, 178, 141, 142, 66, 181, 240, 53, 217, 62, 240, 68, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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