Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b378fd49c95f4877812790add885ced71f53e84915ec4adfad1828d5a27ba44e

Tx prefix hash: d0c6b22d53892e0d71a369d0be4a93f2f0be1b5164b7e3b0359c49be9a0a0706
Tx public key: 8881edbd7b58cdde6a33494ea54b73a6f41dfde4a44626083fc2f824375b2145
Timestamp: 1729317907 Timestamp [UCT]: 2024-10-19 06:05:07 Age [y:d:h:m:s]: 01:029:21:42:17
Block: 1134800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279747 RingCT/type: yes/0
Extra: 018881edbd7b58cdde6a33494ea54b73a6f41dfde4a44626083fc2f824375b21450211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f12d14758292a5a292e0db8893f6b9bd7129c8f9ea910c7bc320074e82d36b37 0.600000000000 1618127 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": 1134810, "vin": [ { "gen": { "height": 1134800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f12d14758292a5a292e0db8893f6b9bd7129c8f9ea910c7bc320074e82d36b37" } } ], "extra": [ 1, 136, 129, 237, 189, 123, 88, 205, 222, 106, 51, 73, 78, 165, 75, 115, 166, 244, 29, 253, 228, 164, 70, 38, 8, 63, 194, 248, 36, 55, 91, 33, 69, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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