Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45c82f44039e9bbbe131a5706e7196343f621d811c775212ac4d6cbd0fd0a3c8

Tx prefix hash: 95643a44d5047bbf0874b66f9253453284487d38411b08f5454e5e9fa4127c8d
Tx public key: 0dcf6f960515dac60a6719bae3500e1781545d2b18fb974e72334241b68bd560
Timestamp: 1735948394 Timestamp [UCT]: 2025-01-03 23:53:14 Age [y:d:h:m:s]: 00:307:23:27:15
Block: 1189646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217611 RingCT/type: yes/0
Extra: 010dcf6f960515dac60a6719bae3500e1781545d2b18fb974e72334241b68bd560021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b56a2232fc2e2c0b577d0a9db1d502a8cb11a93a92c1ffbac5bf8689e9ee291f 0.600000000000 1676157 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": 1189656, "vin": [ { "gen": { "height": 1189646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b56a2232fc2e2c0b577d0a9db1d502a8cb11a93a92c1ffbac5bf8689e9ee291f" } } ], "extra": [ 1, 13, 207, 111, 150, 5, 21, 218, 198, 10, 103, 25, 186, 227, 80, 14, 23, 129, 84, 93, 43, 24, 251, 151, 78, 114, 51, 66, 65, 182, 139, 213, 96, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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