Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43fca65a66d9b248f3b3f72527fbe7f377552750830291c451e26cbfaf1d3d5

Tx prefix hash: 35cd32c58439d06270469400ff8b2e6348d5a3677b21146ab4c8f3557a3a8b24
Tx public key: e3889528c669d562b244262a9ade6e06ecfcc4c0a88e4f6881ef0b6204aa7ea4
Timestamp: 1635964716 Timestamp [UCT]: 2021-11-03 18:38:36 Age [y:d:h:m:s]: 03:095:20:24:27
Block: 366649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 846792 RingCT/type: yes/0
Extra: 01e3889528c669d562b244262a9ade6e06ecfcc4c0a88e4f6881ef0b6204aa7ea40211000000024a0f5013000000000000000000

1 output(s) for total of 37.423125752000 dcy

stealth address amount amount idx
00: 266e0961e276b1d3fb33bde3867d1b6d4417151b2ef9625d405dac5deb9c9769 37.423125752000 744203 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": 366659, "vin": [ { "gen": { "height": 366649 } } ], "vout": [ { "amount": 37423125752, "target": { "key": "266e0961e276b1d3fb33bde3867d1b6d4417151b2ef9625d405dac5deb9c9769" } } ], "extra": [ 1, 227, 136, 149, 40, 198, 105, 213, 98, 178, 68, 38, 42, 154, 222, 110, 6, 236, 252, 196, 192, 168, 142, 79, 104, 129, 239, 11, 98, 4, 170, 126, 164, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 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