Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0fa8fe217bebdf54c0f4bbcec9d516cac2ed683c4e50e3ff1d430c4dfdaabd

Tx prefix hash: 8bc07ad86061cb22c89cfaf883e610c135c29ccc7d4b8e787720a8af609424a9
Tx public key: 5f3b7087957f01fe045597e05aa593ba2f331912df1da50bc65dee1189a64c55
Timestamp: 1706441654 Timestamp [UCT]: 2024-01-28 11:34:14 Age [y:d:h:m:s]: 01:027:10:27:20
Block: 945123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280660 RingCT/type: yes/0
Extra: 015f3b7087957f01fe045597e05aa593ba2f331912df1da50bc65dee1189a64c5502110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f91b45099d4362d582744e5887e9d2f869502e12195382f4aa4ca149bece5bf5 0.600000000000 1403433 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": 945133, "vin": [ { "gen": { "height": 945123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f91b45099d4362d582744e5887e9d2f869502e12195382f4aa4ca149bece5bf5" } } ], "extra": [ 1, 95, 59, 112, 135, 149, 127, 1, 254, 4, 85, 151, 224, 90, 165, 147, 186, 47, 51, 25, 18, 223, 29, 165, 11, 198, 93, 238, 17, 137, 166, 76, 85, 2, 17, 0, 0, 0, 11, 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