Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8fa6e25350e04cbbb96675be2a85917a845b2557a56c883aa94728296dec873

Tx prefix hash: 55fd683943fa59ffba1c1ad9e8461f4e9241892995d4de0a5fab599484abe07c
Tx public key: 4913cccf9672853895117b4a0ea674f4c594267eacfe3f33ee5d790cb6f33c7e
Timestamp: 1672650935 Timestamp [UCT]: 2023-01-02 09:15:35 Age [y:d:h:m:s]: 02:312:10:27:09
Block: 665870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742713 RingCT/type: yes/0
Extra: 014913cccf9672853895117b4a0ea674f4c594267eacfe3f33ee5d790cb6f33c7e021100000004faf35c9c000000000000000000

1 output(s) for total of 3.816772175000 dcy

stealth address amount amount idx
00: c396ef702b7c300bd8a7ec137168400fdf6196ad8bebb2f356c5bead1e975680 3.816772175000 1106939 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": 665880, "vin": [ { "gen": { "height": 665870 } } ], "vout": [ { "amount": 3816772175, "target": { "key": "c396ef702b7c300bd8a7ec137168400fdf6196ad8bebb2f356c5bead1e975680" } } ], "extra": [ 1, 73, 19, 204, 207, 150, 114, 133, 56, 149, 17, 123, 74, 14, 166, 116, 244, 197, 148, 38, 126, 172, 254, 63, 51, 238, 93, 121, 12, 182, 243, 60, 126, 2, 17, 0, 0, 0, 4, 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