Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37fd3f93e002d7a797e128e4621ada01e3d0be9bad1af9aa0651cb182bfb1142

Tx prefix hash: 242766f9885f6f874cb5f00ab4dfcfad7c5f596b775ac31cbc506749b4ef43dc
Tx public key: f79881051080ae8a9bcaf001315a28648fa75aa7aff3061269b429e0679fb2ce
Timestamp: 1710565328 Timestamp [UCT]: 2024-03-16 05:02:08 Age [y:d:h:m:s]: 01:013:03:22:18
Block: 979359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270353 RingCT/type: yes/0
Extra: 01f79881051080ae8a9bcaf001315a28648fa75aa7aff3061269b429e0679fb2ce0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85eede1e1e8ee59a2265f9f772b3c5c7ef2df2f184700096703aa8af15ba3ef9 0.600000000000 1439392 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": 979369, "vin": [ { "gen": { "height": 979359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85eede1e1e8ee59a2265f9f772b3c5c7ef2df2f184700096703aa8af15ba3ef9" } } ], "extra": [ 1, 247, 152, 129, 5, 16, 128, 174, 138, 155, 202, 240, 1, 49, 90, 40, 100, 143, 167, 90, 167, 175, 243, 6, 18, 105, 180, 41, 224, 103, 159, 178, 206, 2, 17, 0, 0, 0, 1, 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