Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38988755d16668628e8374e4ac2cfb35ada6f34c136641ef8d80c980df6a5395

Tx prefix hash: 28185a954f20ba774d528d9ef8cad90d2dc148d05baaeadcf1b80d761b715bb9
Tx public key: 2ef57748565445d44d0619d9f6e6d2a575b61d535491e088c1028f4e0cd1803c
Timestamp: 1713885633 Timestamp [UCT]: 2024-04-23 15:20:33 Age [y:d:h:m:s]: 01:036:14:03:30
Block: 1006870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287105 RingCT/type: yes/0
Extra: 012ef57748565445d44d0619d9f6e6d2a575b61d535491e088c1028f4e0cd1803c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1859e4bef75d2ae5456586c15e86cc3890d1a91e6214a75891ddbe8ab957b89d 0.600000000000 1468032 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": 1006880, "vin": [ { "gen": { "height": 1006870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1859e4bef75d2ae5456586c15e86cc3890d1a91e6214a75891ddbe8ab957b89d" } } ], "extra": [ 1, 46, 245, 119, 72, 86, 84, 69, 212, 77, 6, 25, 217, 246, 230, 210, 165, 117, 182, 29, 83, 84, 145, 224, 136, 193, 2, 143, 78, 12, 209, 128, 60, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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