Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ece0e3ebd419bcf6e744512f6725fd0b032bf16553d282e5a87786413e58c962

Tx prefix hash: 9119d6fa0960af97fbe595ba3f3a33dd2b379ce33b669e9e034c9f96f4b8d7e2
Tx public key: 1839907f9d18f505f9c574110a24611e4897cc217cd5d523e9d736afb50c402d
Timestamp: 1699685051 Timestamp [UCT]: 2023-11-11 06:44:11 Age [y:d:h:m:s]: 01:139:13:12:20
Block: 889134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360921 RingCT/type: yes/0
Extra: 011839907f9d18f505f9c574110a24611e4897cc217cd5d523e9d736afb50c402d02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.694912238000 dcy

stealth address amount amount idx
00: bae32f224a36fcb12b339fef98fb7dc42d449f66f9f6f27d35cf239125d90a38 0.694912238000 1345111 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": 889144, "vin": [ { "gen": { "height": 889134 } } ], "vout": [ { "amount": 694912238, "target": { "key": "bae32f224a36fcb12b339fef98fb7dc42d449f66f9f6f27d35cf239125d90a38" } } ], "extra": [ 1, 24, 57, 144, 127, 157, 24, 245, 5, 249, 197, 116, 17, 10, 36, 97, 30, 72, 151, 204, 33, 124, 213, 213, 35, 233, 215, 54, 175, 181, 12, 64, 45, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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