Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f6c9a504e4f2b393fd1392945fd6844e61e8efe2bec0302c2aa0ed01232dc4

Tx prefix hash: f551bd57ac08105bf329e2028a1f625c90bafc8735bb56228d594d28d2a1ef45
Tx public key: 0fae36c87a20e802556d53f61114ce5a9fd2f32626b406022895c844534bc83a
Timestamp: 1696435455 Timestamp [UCT]: 2023-10-04 16:04:15 Age [y:d:h:m:s]: 01:165:15:41:31
Block: 862390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379441 RingCT/type: yes/0
Extra: 010fae36c87a20e802556d53f61114ce5a9fd2f32626b406022895c844534bc83a0211000000014b8f5122000000000000000000

1 output(s) for total of 0.852204795000 dcy

stealth address amount amount idx
00: 867e84df346822c3defdbd2317361fa9693e395a2874453d09715e5dad45512e 0.852204795000 1316808 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": 862400, "vin": [ { "gen": { "height": 862390 } } ], "vout": [ { "amount": 852204795, "target": { "key": "867e84df346822c3defdbd2317361fa9693e395a2874453d09715e5dad45512e" } } ], "extra": [ 1, 15, 174, 54, 200, 122, 32, 232, 2, 85, 109, 83, 246, 17, 20, 206, 90, 159, 210, 243, 38, 38, 180, 6, 2, 40, 149, 200, 68, 83, 75, 200, 58, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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