Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 576d35197ed7231a25b3f9e9f15c83be19324a1f63ac00b85af66c731d5e41b5

Tx prefix hash: 3cb6b41bc2c213bc8b107bd047727b565839ae0bf0970305ae555b2e5ea2a0cf
Tx public key: b60c7888fe4fefb8a56e84db50e42949757e2c33a8e85d1e9747e150948389cc
Timestamp: 1702473262 Timestamp [UCT]: 2023-12-13 13:14:22 Age [y:d:h:m:s]: 01:121:12:53:29
Block: 912268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347979 RingCT/type: yes/0
Extra: 01b60c7888fe4fefb8a56e84db50e42949757e2c33a8e85d1e9747e150948389cc02110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4193370ce5fbbdb7136a1f6cf9e580a82880d44fbb172303787e78872f8b8bfd 0.600000000000 1369494 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": 912278, "vin": [ { "gen": { "height": 912268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4193370ce5fbbdb7136a1f6cf9e580a82880d44fbb172303787e78872f8b8bfd" } } ], "extra": [ 1, 182, 12, 120, 136, 254, 79, 239, 184, 165, 110, 132, 219, 80, 228, 41, 73, 117, 126, 44, 51, 168, 232, 93, 30, 151, 71, 225, 80, 148, 131, 137, 204, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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