Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2fba79f61a7d6750e7ad97d1271aadad62c32e4febfed907b80dcd9d430a3fa

Tx prefix hash: 666df11155fcd6bd12be0c0cdd6ec4cd9e1abf090bddd6bc73291d75e681f21b
Tx public key: b7d608b1ea875610965544be7d777002e59b33a78245590fd22be0c30ea80837
Timestamp: 1718580929 Timestamp [UCT]: 2024-06-16 23:35:29 Age [y:d:h:m:s]: 00:220:01:52:31
Block: 1045806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157431 RingCT/type: yes/0
Extra: 01b7d608b1ea875610965544be7d777002e59b33a78245590fd22be0c30ea808370211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bbb18a94ddbd9defbe5b871d119e15c1c533e8bc5db6f571d96c0165e6feba4 0.600000000000 1515483 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": 1045816, "vin": [ { "gen": { "height": 1045806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bbb18a94ddbd9defbe5b871d119e15c1c533e8bc5db6f571d96c0165e6feba4" } } ], "extra": [ 1, 183, 214, 8, 177, 234, 135, 86, 16, 150, 85, 68, 190, 125, 119, 112, 2, 229, 155, 51, 167, 130, 69, 89, 15, 210, 43, 224, 195, 14, 168, 8, 55, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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