Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40e8cfd4bcf0c641490cec523879a8ded4632d629ac54c9ac4c6e72e47fcee35

Tx prefix hash: 21c47a8851060f081c9548c0aec88e97dbb7c350456225bdbcbc8a895757c3a6
Tx public key: eb2f2c7072c4c8d6fb6778a73b1bdcc2c8617400a837e49409d7a746195d223a
Timestamp: 1735996947 Timestamp [UCT]: 2025-01-04 13:22:27 Age [y:d:h:m:s]: 00:095:03:18:18
Block: 1190051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67773 RingCT/type: yes/0
Extra: 01eb2f2c7072c4c8d6fb6778a73b1bdcc2c8617400a837e49409d7a746195d223a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec9a36c05d8abafed6b649281f9e6caed0c3ef48355bd136f1cc79fc22ad02e1 0.600000000000 1676566 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": 1190061, "vin": [ { "gen": { "height": 1190051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec9a36c05d8abafed6b649281f9e6caed0c3ef48355bd136f1cc79fc22ad02e1" } } ], "extra": [ 1, 235, 47, 44, 112, 114, 196, 200, 214, 251, 103, 120, 167, 59, 27, 220, 194, 200, 97, 116, 0, 168, 55, 228, 148, 9, 215, 167, 70, 25, 93, 34, 58, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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