Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28bfb67e47bb05aea7899ff027653040c15c8ad4255db5885a16717095bfe1c5

Tx prefix hash: a361e3036d8af176bf10edf7ad6c457e328b7d37b49b566e96d77de7eda35019
Tx public key: ddce645812aa8f2be8e790d06967307310f8b10fd8937cb2f89a9e63a8d14f23
Timestamp: 1694423676 Timestamp [UCT]: 2023-09-11 09:14:36 Age [y:d:h:m:s]: 01:129:20:44:02
Block: 845694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354142 RingCT/type: yes/0
Extra: 01ddce645812aa8f2be8e790d06967307310f8b10fd8937cb2f89a9e63a8d14f2302110000000ffaf35c9c000000000000000000

1 output(s) for total of 0.967976417000 dcy

stealth address amount amount idx
00: 1a02d3f8dcb6852eb214b0acb222c8070a10e6209ca187a97c7064150bec5982 0.967976417000 1299106 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": 845704, "vin": [ { "gen": { "height": 845694 } } ], "vout": [ { "amount": 967976417, "target": { "key": "1a02d3f8dcb6852eb214b0acb222c8070a10e6209ca187a97c7064150bec5982" } } ], "extra": [ 1, 221, 206, 100, 88, 18, 170, 143, 43, 232, 231, 144, 208, 105, 103, 48, 115, 16, 248, 177, 15, 216, 147, 124, 178, 248, 154, 158, 99, 168, 209, 79, 35, 2, 17, 0, 0, 0, 15, 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