Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa45f3fdf514de48c846f86e03eac424b673a14b086dd4b31fe54c2cf55471e2

Tx prefix hash: 35d828895b35632dc5e173ee93730d71eaf67edbe31974ec59b151914139d6d7
Tx public key: 47bde713e0e3e01b30e815abf464fa91f5163bfce2c5ef68bfa9f3801d5c6311
Timestamp: 1706693490 Timestamp [UCT]: 2024-01-31 09:31:30 Age [y:d:h:m:s]: 01:024:19:08:02
Block: 947222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278757 RingCT/type: yes/0
Extra: 0147bde713e0e3e01b30e815abf464fa91f5163bfce2c5ef68bfa9f3801d5c631102110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7f0f3e52b0e37a9e9b00071ce68513ac1f948cd85c95114fe8314842253e7ed 0.600000000000 1405570 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": 947232, "vin": [ { "gen": { "height": 947222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7f0f3e52b0e37a9e9b00071ce68513ac1f948cd85c95114fe8314842253e7ed" } } ], "extra": [ 1, 71, 189, 231, 19, 224, 227, 224, 27, 48, 232, 21, 171, 244, 100, 250, 145, 245, 22, 59, 252, 226, 197, 239, 104, 191, 169, 243, 128, 29, 92, 99, 17, 2, 17, 0, 0, 0, 9, 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