Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2261c798eb98737d4c6431f477aeff87b739a45b7a24ea97d4b8a818cdab891

Tx prefix hash: 0350ebbf37b34647201660c2ebc309b1d64b549db9edd5bdffc1927d30a620e6
Tx public key: 2f5c3be3c3cd931bce05c4c02ff568d828b76abcf2d3b60fa9c1a5ad7796cf63
Timestamp: 1722731331 Timestamp [UCT]: 2024-08-04 00:28:51 Age [y:d:h:m:s]: 00:174:03:42:06
Block: 1080200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124548 RingCT/type: yes/0
Extra: 012f5c3be3c3cd931bce05c4c02ff568d828b76abcf2d3b60fa9c1a5ad7796cf63021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b0d2b996d582d07c047c31e16c1fed72e72140888704f177d7678709fc8a5ae 0.600000000000 1553469 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": 1080210, "vin": [ { "gen": { "height": 1080200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b0d2b996d582d07c047c31e16c1fed72e72140888704f177d7678709fc8a5ae" } } ], "extra": [ 1, 47, 92, 59, 227, 195, 205, 147, 27, 206, 5, 196, 192, 47, 245, 104, 216, 40, 183, 106, 188, 242, 211, 182, 15, 169, 193, 165, 173, 119, 150, 207, 99, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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